We would like to use the Keyshot Render Images script to render a number of Creo .prt files. We find that the .prt files are very hit or miss on whether they will import into keyshot. Either they do and it works great, or they don’t and they throw a no geometry error. Does anyone know the rhyme or reason as to why some would and some wouldn’t work? they’re all from the same groups of files and assemblies, but just randomly some work and some don’t.
To get to this point we basically add the files to our workspace in Windchill and then export the workspace which copies out all the .prt and .asm files to a folder on our c drive or server. From here we would like to run the script to open and render each part. But just in testing even importing the parts manually they throw the error and don’t import, but some do. This is seen from multiple models pulled my multiple people on multiple machines, so I can’t say it’s relevant to 1 particular set of models or even just myself pulling them.
Any thoughts or ideas? For reference we are still KS 11.3.3 until our IT gets our new licenses ready.
Hard to tell without files to check but maybe you can contact support and give them some working and non-working files? Might be sensitive models so maybe you can create a few fakes that show the same behaviour?
I guess the version of Crea on every machine is the same as well as the export settings to get them to the C-drive on the server?
A reason that might cause it is because the files are still in some kind of ‘locked’ state, although that would be a bit weird if it’s about exported files. I’ve no experience with Creo but that’s basically the only thing I can think off. Or export settings are a bit different on the workstations but that would mean the models not working all being exported from a single machine.
I’m a little late here… in my experience an .ASM is what you want to import because it contains the part placement information. It’s been a while but I remember there were times when importing .PRT files the geo imports at the origin. It is possible to script a batch import.
I recommend to use the KeyShot plug-in in Creo and export the BIP file. This way transfers the most infos like camera, simplified reps, family table instances, flexible components, results of Pro/PROGRAM, assembly cuts on component level, meshes. Everything listed will be not loaded when ASM import directly.
Limitation are cables, datum’s, body names, empty subassemblies and curves. Then I would use a neutral format like Step.
This exported BIP file can be used in older KeyShot versions. Creo9 Plug-in works in Creo10.
No geometry errors can appear, a part has not geometry visible to tesselate.
In my humble experiences in > 10 y in KeyShot (and also HyperShot) and > 16 y in Creo Parametric (AKA Pro/ENGINEER)